---
nm: 255.255.255.0
gw: 10.5.125.254
dns: 10.5.126.21
ks_url: http://10.5.126.23/repo/rhel/ks/kvm-rhel-7
ks_repo: http://10.5.126.23/repo/rhel/RHEL7-x86_64/
volgroup: /dev/vg_Server
eth0_ip: 10.5.125.135
eth1_ip: 10.5.127.61
vmhost: bvirthost10.phx2.fedoraproject.org
mem_size: 65536

# These set a config value in /etc/fedmsg.d/, see roles/bodhi2/base/
bodhi_masher_enabled: True
bodhi_updates_handler_enabled: False

# These are consumed by a task in roles/fedmsg/base/main.yml
fedmsg_certs:
# This first cert is used by the push-tool.   releng members run it and it fires
# off a simple fedmsg message that the masher (running as fedmsg-hub) is
# listening for.  It then does all the worker.
- service: shell
  owner: root
  group: masher
  can_send:
  - bodhi.masher.start
# These are certs for the masher to publish its own messages as it progresses.
- service: bodhi
  owner: root
  group: masher
  can_send:
  - bodhi.mashtask.complete
  - bodhi.mashtask.mashing
  - bodhi.mashtask.start
  - bodhi.mashtask.sync.done
  - bodhi.mashtask.sync.wait
  - bodhi.errata.publish
  - bodhi.update.eject
  - bodhi.update.complete.testing
  - bodhi.update.complete.stable
  - bodhi.buildroot_override.untag
- service: ftpsync
  owner: root
  group: ftpsync
  can_send:
  - bodhi.updates.epel.sync
  - bodhi.updates.fedora.sync
- service: releng
  owner: root
  group: sysadmin-releng
  can_send:
  - releng.atomic.twoweek.begin
  - releng.atomic.twoweek.complete


# For the MOTD
csi_security_category: Medium
csi_primary_contact: Releng Admins sysadmin-releng-members@fedoraproject.org
csi_purpose: Run the Bodhi masher.
csi_relationship: |
    The mashing of repos here happens as part of the 'fedmsg-hub' daemon.  Check
    logs with 'journalctl -u fedmsg-hub'.  Check the bodhi masher docs/code for
    more detail on what it does:
    https://github.com/fedora-infra/bodhi/blob/develop/bodhi/consumers/masher.py

    * This host relies on:
      * db01 for its database, which is shares with the bodhi2 frontend nodes.
      * An NFS mount of koji data in /mnt/koji/
      * The fedmsg bus for triggering mashes.
      * XMLRPC calls to koji for tagging and untagging updates.
      * bugzilla for posting comments about status changes
      * the wiki for getting information about QA "Test Cases"
      * taksotron (resultsdb) for getting status-check results (gating updates).

    * No other systems rely directly on this host.  Everything depends on it
      indirectly for the creation of new updates repos (which get synced out to
      the master mirror for distribution.
